• Create ticket/issue

Follow the guide to enable codebase context checks.

Objective: Ensure all identifiers clearly express their purpose and intent, making code
self-documenting

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Objective: To create a detailed and reliable record of critical system actions for security analysis
and compliance.

Status:
No logging context: The change only updates a protobuf field number and does not add or modify any audit
logging for critical actions, which may be outside the scope of this PR.

// Extend EnumValueOptions to include error information for enum values
extend google.protobuf.EnumValueOptions {
  // Provides additional information about error conditions for automated
  // code generation and documentation.
  optional ErrorMetadata error = 2113;

Learn more about managing compliance generic rules or creating your own custom rules

Objective: Ensure comprehensive error handling that provides meaningful context and graceful
degradation

Status:
No error handling: The diff changes only a protobuf option field number and introduces no runtime error
handling or edge-case logic, which may be handled elsewhere.

// Extend EnumValueOptions to include error information for enum values
extend google.protobuf.EnumValueOptions {
  // Provides additional information about error conditions for automated
  // code generation and documentation.
  optional ErrorMetadata error = 2113;

Learn more about managing compliance generic rules or creating your own custom rules

Objective: To prevent the leakage of sensitive system information through error messages while
providing sufficient detail for internal debugging.

Status:
User-facing detail risk: The change references error metadata in protobuf options but does not indicate how
user-facing errors are rendered, which is outside this diff.

// Extend EnumValueOptions to include error information for enum values
extend google.protobuf.EnumValueOptions {
  // Provides additional information about error conditions for automated
  // code generation and documentation.
  optional ErrorMetadata error = 2113;

Learn more about managing compliance generic rules or creating your own custom rules

Objective: To ensure logs are useful for debugging and auditing without exposing sensitive
information like PII, PHI, or cardholder data.

Status:
Logging not shown: No logging is added or modified in this change; compliance cannot be assessed from this
diff alone.

// Extend EnumValueOptions to include error information for enum values
extend google.protobuf.EnumValueOptions {
  // Provides additional information about error conditions for automated
  // code generation and documentation.
  optional ErrorMetadata error = 2113;

Learn more about managing compliance generic rules or creating your own custom rules

Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent
vulnerabilities

Status:
No input validation: The protobuf option field renumbering does not involve input handling or validation, so
security validation cannot be determined from this change.

// Extend EnumValueOptions to include error information for enum values
extend google.protobuf.EnumValueOptions {
  // Provides additional information about error conditions for automated
  // code generation and documentation.
  optional ErrorMetadata error = 2113;

Learn more about managing compliance generic rules or creating your own custom rules

Revert the field number for the custom option error to a value within the
recommended range (50000-536,870,911) to avoid potential conflicts with standard
protobuf options.

src/main/proto/kurrentdb/protocol/v2/rpc.proto [76]

-optional ErrorMetadata error = 2113;
+optional ErrorMetadata error = 50000;

• Apply / Chat